-
Notifications
You must be signed in to change notification settings - Fork 893
fix "no constructor defined" messages on PyPy #5329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
src/pyclass/create_type_object.rs
Outdated
| /// Default new implementation | ||
| #[cfg(not(all(Py_3_10, not(PyPy))))] | ||
| /// Default new implementation, to match | ||
| /// <https://github.com/python/cpython/blob/3663b2ad54c9e15775a605facf69da8f5ee8d335/Objects/typeobject.c#L2427-L2428> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if this comment still makes sense. I guess the output should be identical still..
Also I think the #[cfg(not(PyPy))] in the trampoline below needs to go now, because PyPy does the same thing as CPython now, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for catching, sorry for my shoddy patch 😂
* fix "cannot create '%s' instances" message to match CPython * don't use unlimited C API directly * review feedback * fixup * fixup xfail on PyPy
Has been fixed upstream, let's simplify and xfail for now, the next PyPy patch release will fix this.